Replace UserDiscoverer with stripped back ServerUserProvider. #3067
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The idea of the UserManager is to manage User objects, not GameProfiles. While we do some operations with GameProfiles, they mirror what Users we think have been created - we're not caching
GameProfile
s.The file system watching is in, but all GameProfile caching is delegated to the PlayerProfileCache, which we just get profiles from when required.
It needs some testing, but it seems to at least grab the right user file and I can see it stores the UUIDs of the files that exist - which is the point really.
Note that I have not brought over the notion that banned/whitelisted profiles necessarily have a
User
attached - they don't! If you want a users associated with a banned player, get the banned user's profile and create it.Closes #3059